home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
bbs
/
ripky302.zip
/
RIPKY302.ARJ
/
SYSOP.DOC
< prev
Wrap
Text File
|
1997-03-15
|
4KB
|
77 lines
INSTALLING CARLTON DOORS: GENERATION III
-------------------------------------------------------------------------------
Installation And Set-Up: "It's All The Same"
GENERATION III Doors all use the same installation procedure. If this is your
first time setting up a Carlton Generation III (CG3) door, run the MAKENODE.EXE
utility to create the file CARLTON.INF
Once you run MAKENODE.EXE one time to create your BBS's definition, you won't
ever need to run it again unless you change or add a node to your BBS.
-------------------------------------------------------------------------------
MAKENODE.EXE: Explained
The COMMON DIRECTORY is a directory that ALL nodes have access to. Typically
this would be the main directory where the BBS Program resides.
Answer questions A-F for each of the nodes. For the more technical questions
(like the base addresses for your port) infomational windows appear at the
bottom of the screen, informing you of your typical "standard" choices. If
you have specially configured ports or non-standard IRQ's on your system,
set up the door with the correct information. If you can successfully run
a non-standard port, my doors will operate on them.
If you run a "local only" node on your BBS, set it up as if it's on a standard
node on COM1:. Answer every question for each node.
-------------------------------------------------------------------------------
Configuring A Door: "It's Easy!"
Run INSTALL.EXE or rename and edit the SAMPLE.CFG included with every archive.
Sample.Cfg is a commented ASCII file.
-------------------------------------------------------------------------------
Running A Door: "It Takes No Effort"
Once you have a CARLTON.INF in your common directory, and your .CFG file
reflects the door's configuration, all that's left is to run the door.
The command line to run a door is DOORNAME # (# is the number of the node
accessing the file). For instance, to run SIMPLE PLEASURES on node #2, the
command line is: SIMPLE 2
To run a door in local mode (without starting the BBS) you can either just
use the doorname, or you can use a zero for the node number.
-------------------------------------------------------------------------------
Generation History:
There are three generations of CARLTON doors being distributed. The Generation
I.D. deals specifically with the library I used to write the door.
The first generation was written using a modified CATPATCH library...
originally designed specifically for writing Wildcat! doors. This library
was greatly expanded and modified for my own doors. It worked well, but had
many limitations... (baud rates of 9600 and below only!)
The second generation was written using DoorFrame by the late Ted Freeman.
While this library gave me much more flexibility than the Generation One
library, I was at the mercy of the support BBS to correct any library
errors... and it was those library errors that cost me many registrations
when I couldn't correct the problem.
Between the second and third generations, I flirted with an unregistered
copy of Insta-Door. While the code seemed clean, I was unable to locate
a support BBS, any of the authors, and anybody else using the library.
If you encounter any of these doors (5 second blank-screen going into the
door) archive it (for museum viewing) and call and get the latest version
from SOMEPLACE ELSE BBS. Insta-Door versions of my doors are not supported.
Generation III is my own code. I looked at the routines used by many other
of the pre-compiled libraries, and while I couldn't view their code, I looked
at how their routines worked and acted together. I asked other SYSOPs about
what they did (and didn't like) about door set-ups. And GENERATION III was
the direct result. I hope you enjoy my work.